Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87b5c40d58ea2578547cfa0735a05a2d1c271bfdaacdc034b497cb9b304849e2

Tx prefix hash: 4fe761e405fe85dc4cf771702adbfe889a197ee27d14c92ca6c047f51e766c9e
Tx public key: 81f8e9199ecb21c998ddad0365f6ebdfb6048398198ae66c367167fb7b8ea783
Timestamp: 1580978258 Timestamp [UCT]: 2020-02-06 08:37:38 Age [y:d:h:m:s]: 04:362:03:07:36
Block: 59774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149984 RingCT/type: yes/0
Extra: 0181f8e9199ecb21c998ddad0365f6ebdfb6048398198ae66c367167fb7b8ea78302110000000156c366d3000000000000000000

1 output(s) for total of 389.019498658000 dcy

stealth address amount amount idx
00: 8736c5d84a2ce5b62027d98ce3bf2589540c5251941416e22565512fb65f9c44 389.019498658000 110280 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": 59784, "vin": [ { "gen": { "height": 59774 } } ], "vout": [ { "amount": 389019498658, "target": { "key": "8736c5d84a2ce5b62027d98ce3bf2589540c5251941416e22565512fb65f9c44" } } ], "extra": [ 1, 129, 248, 233, 25, 158, 203, 33, 201, 152, 221, 173, 3, 101, 246, 235, 223, 182, 4, 131, 152, 25, 138, 230, 108, 54, 113, 103, 251, 123, 142, 167, 131, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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