Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6d69f0335c32966ec6aee642b9b583afff687c3a0f08a3c91e7f108b593a04f

Tx prefix hash: 01053e083f49d5ddafcd9bad1ca31a54b66ca3c1b524e79058ef27f4b7674785
Tx public key: 9c0f73a67bd0ba407d449f1ddf40981e810a680c60d22734efe51e68933fb3e3
Timestamp: 1712695223 Timestamp [UCT]: 2024-04-09 20:40:23 Age [y:d:h:m:s]: 01:044:14:07:17
Block: 996970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292877 RingCT/type: yes/0
Extra: 019c0f73a67bd0ba407d449f1ddf40981e810a680c60d22734efe51e68933fb3e30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d30554c7ff5d6d1545ed71052d2c6ad1557f110d6f7a1c6c795d62e440fd5b00 0.600000000000 1457398 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": 996980, "vin": [ { "gen": { "height": 996970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d30554c7ff5d6d1545ed71052d2c6ad1557f110d6f7a1c6c795d62e440fd5b00" } } ], "extra": [ 1, 156, 15, 115, 166, 123, 208, 186, 64, 125, 68, 159, 29, 223, 64, 152, 30, 129, 10, 104, 12, 96, 210, 39, 52, 239, 229, 30, 104, 147, 63, 179, 227, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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