Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe76fc4b20268d5437cfe86412e018c8421b9462bb5a6767088e2d71eaad93f

Tx prefix hash: 79cb5fe3ec281a4e855920b4471a6ce26aa312c9e396fdab799f53b1a5336cbf
Tx public key: 45a9f11737723f8cbc1f1b3dfaf1ceec7724e7dfc5e20b0cfd49190e14d4831a
Timestamp: 1712770407 Timestamp [UCT]: 2024-04-10 17:33:27 Age [y:d:h:m:s]: 00:352:12:35:11
Block: 997597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252046 RingCT/type: yes/0
Extra: 0145a9f11737723f8cbc1f1b3dfaf1ceec7724e7dfc5e20b0cfd49190e14d4831a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32341634ab05abf0f25331100ae33f43feff090e2067f32160370b7cc4a63fb3 0.600000000000 1458031 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": 997607, "vin": [ { "gen": { "height": 997597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32341634ab05abf0f25331100ae33f43feff090e2067f32160370b7cc4a63fb3" } } ], "extra": [ 1, 69, 169, 241, 23, 55, 114, 63, 140, 188, 31, 27, 61, 250, 241, 206, 236, 119, 36, 231, 223, 197, 226, 11, 12, 253, 73, 25, 14, 20, 212, 131, 26, 2, 17, 0, 0, 0, 2, 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