Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f85e1f4eb4456faa6cb5c40b0a14fa6293900a8c7bf30742a65548bc601e82

Tx prefix hash: 7cf43ff509642af81d35c5bdedda96c45cf4940ddd0a7ce1601c9747f56bb3f4
Tx public key: eb3e173b22e5c7f60267d13c5b5d9d8d441b37ec273949707d5df6552b179e0a
Timestamp: 1709041203 Timestamp [UCT]: 2024-02-27 13:40:03 Age [y:d:h:m:s]: 01:066:12:42:59
Block: 966708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308573 RingCT/type: yes/0
Extra: 01eb3e173b22e5c7f60267d13c5b5d9d8d441b37ec273949707d5df6552b179e0a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dab117af1c6c4149d837350df45fbbbccb5985085531092ab1b6660e8d147e4 0.600000000000 1426479 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": 966718, "vin": [ { "gen": { "height": 966708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dab117af1c6c4149d837350df45fbbbccb5985085531092ab1b6660e8d147e4" } } ], "extra": [ 1, 235, 62, 23, 59, 34, 229, 199, 246, 2, 103, 209, 60, 91, 93, 157, 141, 68, 27, 55, 236, 39, 57, 73, 112, 125, 93, 246, 85, 43, 23, 158, 10, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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