Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b11997b0a35b656c6beabea0c74b4d838bef0050ebf3dbb243a0d6b1250e3e6

Tx prefix hash: 25ba5bd26569026e8568e4bd40d7aa8bc8d48709096ecbbe0af9a719e06cc32e
Tx public key: 3902533cc00f16b89d9bdee466cfaa8b3d5a7e01910c49dbbbe9c14a265ef2ae
Timestamp: 1581364711 Timestamp [UCT]: 2020-02-10 19:58:31 Age [y:d:h:m:s]: 04:362:01:47:04
Block: 62244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150668 RingCT/type: yes/0
Extra: 013902533cc00f16b89d9bdee466cfaa8b3d5a7e01910c49dbbbe9c14a265ef2ae02110000010d03d36d11000000000000000000

1 output(s) for total of 381.733790136000 dcy

stealth address amount amount idx
00: 31dd99335320850fe5d10beebd845424a06a99784f8f42a9d014bf21d9672608 381.733790136000 114787 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": 62254, "vin": [ { "gen": { "height": 62244 } } ], "vout": [ { "amount": 381733790136, "target": { "key": "31dd99335320850fe5d10beebd845424a06a99784f8f42a9d014bf21d9672608" } } ], "extra": [ 1, 57, 2, 83, 60, 192, 15, 22, 184, 157, 155, 222, 228, 102, 207, 170, 139, 61, 90, 126, 1, 145, 12, 73, 219, 187, 233, 193, 74, 38, 94, 242, 174, 2, 17, 0, 0, 1, 13, 3, 211, 109, 17, 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