Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc039502c126bd37d111c89af1a8af4d0f8a2be95f120ddd6c4a09036aca4dab

Tx prefix hash: a8f1b54ff11aaa379a677ec54bdf461fbbcdc8e05bc04969a8a921ae850b88f3
Tx public key: e14f5befaaeac2c3086d9a5d52e8a58510173dad9a8d4e25d06a2f1d79e7855e
Timestamp: 1578487914 Timestamp [UCT]: 2020-01-08 12:51:54 Age [y:d:h:m:s]: 04:326:22:54:23
Block: 41255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122984 RingCT/type: yes/0
Extra: 01e14f5befaaeac2c3086d9a5d52e8a58510173dad9a8d4e25d06a2f1d79e7855e021100000010391a8d0e000000000000000000

1 output(s) for total of 448.028772144000 dcy

stealth address amount amount idx
00: 259b646dd567b794aaa7a9d8a594028c5d90cae83241821629546555fd0360d3 448.028772144000 73307 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": 41265, "vin": [ { "gen": { "height": 41255 } } ], "vout": [ { "amount": 448028772144, "target": { "key": "259b646dd567b794aaa7a9d8a594028c5d90cae83241821629546555fd0360d3" } } ], "extra": [ 1, 225, 79, 91, 239, 170, 234, 194, 195, 8, 109, 154, 93, 82, 232, 165, 133, 16, 23, 61, 173, 154, 141, 78, 37, 208, 106, 47, 29, 121, 231, 133, 94, 2, 17, 0, 0, 0, 16, 57, 26, 141, 14, 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