Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c7d3c6dce05ad3051877a39104660f3579c7e4cda1b7b02d78cc315d505ace0

Tx prefix hash: 9aa204d86dd39dbced777173c2cba862e399203ebc064716fead310490558083
Tx public key: f4ca00a418a5abadf8b502f9e98bf4116aea0ff76b4342c910a9c6ca287e1636
Timestamp: 1705410123 Timestamp [UCT]: 2024-01-16 13:02:03 Age [y:d:h:m:s]: 01:039:22:53:50
Block: 936570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289630 RingCT/type: yes/0
Extra: 01f4ca00a418a5abadf8b502f9e98bf4116aea0ff76b4342c910a9c6ca287e16360211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e544364d007190e1d1554cf74e079aa42044f7a4a63867fbe98930726b41e8f 0.600000000000 1394598 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": 936580, "vin": [ { "gen": { "height": 936570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e544364d007190e1d1554cf74e079aa42044f7a4a63867fbe98930726b41e8f" } } ], "extra": [ 1, 244, 202, 0, 164, 24, 165, 171, 173, 248, 181, 2, 249, 233, 139, 244, 17, 106, 234, 15, 247, 107, 67, 66, 201, 16, 169, 198, 202, 40, 126, 22, 54, 2, 17, 0, 0, 0, 7, 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