Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e1a5577fbbf7739634e85021e09a2e49f15f965742fe2d257f91849c0a27086

Tx prefix hash: ee99afc7fdd317a82843e7e356d1e66138c1f0f66581dbd670db4dfb8176f209
Tx public key: 954f3f230e2d68c66ebf729cb019fe6a8650e3c262f62465f96cc0b10b78e656
Timestamp: 1676418999 Timestamp [UCT]: 2023-02-14 23:56:39 Age [y:d:h:m:s]: 02:057:20:48:10
Block: 697143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562948 RingCT/type: yes/0
Extra: 01954f3f230e2d68c66ebf729cb019fe6a8650e3c262f62465f96cc0b10b78e656021100000002faf35c9c000000000000000000

1 output(s) for total of 3.006600744000 dcy

stealth address amount amount idx
00: eaeedaec52db87fe8ab66ddf28544f6da4b4ff31c6da036214bcd3124b4c5f89 3.006600744000 1140252 of 0

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": 697153, "vin": [ { "gen": { "height": 697143 } } ], "vout": [ { "amount": 3006600744, "target": { "key": "eaeedaec52db87fe8ab66ddf28544f6da4b4ff31c6da036214bcd3124b4c5f89" } } ], "extra": [ 1, 149, 79, 63, 35, 14, 45, 104, 198, 110, 191, 114, 156, 176, 25, 254, 106, 134, 80, 227, 194, 98, 246, 36, 101, 249, 108, 192, 177, 11, 120, 230, 86, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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