Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a906688cc65fc6b57882b1934f8ff6e1f7b00b5dbf15ffd0ea51a8e77501a4

Tx prefix hash: e6616d351dc33847c8a4e815f5a67e5d22f08d2ac2b3c602f27a2bf93ab192aa
Tx public key: f981d0e3d88dc9a70b45179fc22942286e2a9036924e2d6269ccbab7543a0a3d
Timestamp: 1702359737 Timestamp [UCT]: 2023-12-12 05:42:17 Age [y:d:h:m:s]: 01:360:23:45:07
Block: 911306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516894 RingCT/type: yes/0
Extra: 01f981d0e3d88dc9a70b45179fc22942286e2a9036924e2d6269ccbab7543a0a3d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee11d9dd08f86ff0d1a927288e7c46ede5952b6cf9c4f3adecb53aa5ebaf2af5 0.600000000000 1368487 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": 911316, "vin": [ { "gen": { "height": 911306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee11d9dd08f86ff0d1a927288e7c46ede5952b6cf9c4f3adecb53aa5ebaf2af5" } } ], "extra": [ 1, 249, 129, 208, 227, 216, 141, 201, 167, 11, 69, 23, 159, 194, 41, 66, 40, 110, 42, 144, 54, 146, 78, 45, 98, 105, 204, 186, 183, 84, 58, 10, 61, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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