Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f270e78113d09d2abb0c7609769ebc7dfb1929494591b9ea83d2b638782607d6

Tx prefix hash: 918cbfa5d58179d2480ddbc278822b3d286541fdb2c254e4db5d1ee662a841ce
Tx public key: 44dde502a92b9d1b112323b3f90bb17f9a67cc5ed7ee7d8228eb6bb527a01081
Timestamp: 1716752154 Timestamp [UCT]: 2024-05-26 19:35:54 Age [y:d:h:m:s]: 00:294:07:12:47
Block: 1030645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210329 RingCT/type: yes/0
Extra: 0144dde502a92b9d1b112323b3f90bb17f9a67cc5ed7ee7d8228eb6bb527a0108102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bbfcae3812b77adb1fba3cd1fa7e841dcc9768d6556e10523f8fb39a0535c24 0.600000000000 1498902 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": 1030655, "vin": [ { "gen": { "height": 1030645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bbfcae3812b77adb1fba3cd1fa7e841dcc9768d6556e10523f8fb39a0535c24" } } ], "extra": [ 1, 68, 221, 229, 2, 169, 43, 157, 27, 17, 35, 35, 179, 249, 11, 177, 127, 154, 103, 204, 94, 215, 238, 125, 130, 40, 235, 107, 181, 39, 160, 16, 129, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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