Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6dce7f5861132719d3915284e1ee9acfcf05c06a10dcea74e60960a3d49be2

Tx prefix hash: 3a36d096a3a7a89ed2b83037e820d30c3d088335d563ebd031a04a114c07f25e
Tx public key: ecf9df4222dc4f7626edba83f0e702ea7a71795757af386c2f6534071126649d
Timestamp: 1732747531 Timestamp [UCT]: 2024-11-27 22:45:31 Age [y:d:h:m:s]: 00:128:12:06:47
Block: 1163136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91656 RingCT/type: yes/0
Extra: 01ecf9df4222dc4f7626edba83f0e702ea7a71795757af386c2f6534071126649d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb26dfd7dc9d488b8f7ed2ba2e2f690b610b4ef7977a696bc2c507e8f62cf85 0.600000000000 1648803 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": 1163146, "vin": [ { "gen": { "height": 1163136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb26dfd7dc9d488b8f7ed2ba2e2f690b610b4ef7977a696bc2c507e8f62cf85" } } ], "extra": [ 1, 236, 249, 223, 66, 34, 220, 79, 118, 38, 237, 186, 131, 240, 231, 2, 234, 122, 113, 121, 87, 87, 175, 56, 108, 47, 101, 52, 7, 17, 38, 100, 157, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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