Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 246ced96510b9138d0fcee6663712a4c9f556d3b97b50b16404324c524c30863

Tx prefix hash: 23db96e35ed57b1419e83b874449b72ce13ef15ea48baf31ec5c34fd762f3e4e
Tx public key: a5fc0e7bb9daa25d70aac38cd18351661d9f0d0318d0ffff2bdad8d031bdecbc
Timestamp: 1734231211 Timestamp [UCT]: 2024-12-15 02:53:31 Age [y:d:h:m:s]: 00:108:03:55:41
Block: 1175455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77057 RingCT/type: yes/0
Extra: 01a5fc0e7bb9daa25d70aac38cd18351661d9f0d0318d0ffff2bdad8d031bdecbc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd97fbc440281a2d0744cc763bbb407e2aeb7c86cd51a5c416964773a2d0a8aa 0.600000000000 1661738 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": 1175465, "vin": [ { "gen": { "height": 1175455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd97fbc440281a2d0744cc763bbb407e2aeb7c86cd51a5c416964773a2d0a8aa" } } ], "extra": [ 1, 165, 252, 14, 123, 185, 218, 162, 93, 112, 170, 195, 140, 209, 131, 81, 102, 29, 159, 13, 3, 24, 208, 255, 255, 43, 218, 216, 208, 49, 189, 236, 188, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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