Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d42a7d8199b1af7520af98c91d59faa400cadc60b731352cf8d6cf04dea2e0

Tx prefix hash: 49e844278313d3b3712eb81658bf12d7a7f7042630eb5644bd64828dcb70bbaa
Tx public key: 37935d4a6d77f6c3f6c7e7e6d28d26a7d3a723bf2960656e0909ae17c1537dca
Timestamp: 1711122573 Timestamp [UCT]: 2024-03-22 15:49:33 Age [y:d:h:m:s]: 00:293:17:25:23
Block: 983980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210236 RingCT/type: yes/0
Extra: 0137935d4a6d77f6c3f6c7e7e6d28d26a7d3a723bf2960656e0909ae17c1537dca0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 040aa9c4ee34bd666e981a2f00f81370fdd01a03c9178f67ee1350e23004473e 0.600000000000 1444133 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": 983990, "vin": [ { "gen": { "height": 983980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040aa9c4ee34bd666e981a2f00f81370fdd01a03c9178f67ee1350e23004473e" } } ], "extra": [ 1, 55, 147, 93, 74, 109, 119, 246, 195, 246, 199, 231, 230, 210, 141, 38, 167, 211, 167, 35, 191, 41, 96, 101, 110, 9, 9, 174, 23, 193, 83, 125, 202, 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