Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d9dd3f0437e7ff819aac7e11a60c5846456bc6a540fae0718bdeb615941ba07

Tx prefix hash: fed69b4021da890a6fff19ba1fd8a359491cbb6a9d197506a1e2b61cac662877
Tx public key: 516b3e29d03e1b1663cce3dfc202fe20247bbce5b99d364eeb99adfd10f1e281
Timestamp: 1681229354 Timestamp [UCT]: 2023-04-11 16:09:14 Age [y:d:h:m:s]: 02:007:19:11:22
Block: 736371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527736 RingCT/type: yes/0
Extra: 01516b3e29d03e1b1663cce3dfc202fe20247bbce5b99d364eeb99adfd10f1e281021100000001b3164c24000000000000000000

1 output(s) for total of 2.228935073000 dcy

stealth address amount amount idx
00: d6347307e5765b12a7bf37f0f49be0ce3f19e09d6914c48d3dc9233c7ac23aa8 2.228935073000 1182798 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": 736381, "vin": [ { "gen": { "height": 736371 } } ], "vout": [ { "amount": 2228935073, "target": { "key": "d6347307e5765b12a7bf37f0f49be0ce3f19e09d6914c48d3dc9233c7ac23aa8" } } ], "extra": [ 1, 81, 107, 62, 41, 208, 62, 27, 22, 99, 204, 227, 223, 194, 2, 254, 32, 36, 123, 188, 229, 185, 157, 54, 78, 235, 153, 173, 253, 16, 241, 226, 129, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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