Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fc289cacd7dc29e1e840f64148108f35602394c809bfe17e1e36f320b83ea625

Tx prefix hash: 135d1dde4665ffca8670562abdb7bfdeb2903d6df52fd0195d1f41c622c7fe8e
Tx public key: e50464835ae30eaf5d16c0f54b33c64e3faf6b95d73c45cd0ae4b346d075c622
Timestamp: 1716646962 Timestamp [UCT]: 2024-05-25 14:22:42 Age [y:d:h:m:s]: 00:243:19:38:34
Block: 1029760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174447 RingCT/type: yes/0
Extra: 01e50464835ae30eaf5d16c0f54b33c64e3faf6b95d73c45cd0ae4b346d075c6220211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a1d7940d491da1dd237a10705df3ac1daf1f2a40049bf96b6fa0560daaaa5b 0.600000000000 1497941 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1029770, "vin": [ { "gen": { "height": 1029760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a1d7940d491da1dd237a10705df3ac1daf1f2a40049bf96b6fa0560daaaa5b" } } ], "extra": [ 1, 229, 4, 100, 131, 90, 227, 14, 175, 93, 22, 192, 245, 75, 51, 198, 78, 63, 175, 107, 149, 215, 60, 69, 205, 10, 228, 179, 70, 208, 117, 198, 34, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8