Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e542a09d98f18451c11432a62f4d86e672218def70f21ea468868fa28a03c0fb

Tx prefix hash: 69dddaa160d20cdea9cfd8337bfc9da289f912124e55777dfad1f4dab4dc8f3a
Tx public key: 68e1b634199b6cea5dd1ea1ac3f3c83ea5de2eb7c72900ede5cb6eb26b638a9c
Timestamp: 1736663232 Timestamp [UCT]: 2025-01-12 06:27:12 Age [y:d:h:m:s]: 00:060:05:32:27
Block: 1195560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42838 RingCT/type: yes/0
Extra: 0168e1b634199b6cea5dd1ea1ac3f3c83ea5de2eb7c72900ede5cb6eb26b638a9c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d8cd96f225fa6d4a474d7868280d1e00d14b158ce020b829c06ff96beac088 0.600000000000 1682151 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": 1195570, "vin": [ { "gen": { "height": 1195560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d8cd96f225fa6d4a474d7868280d1e00d14b158ce020b829c06ff96beac088" } } ], "extra": [ 1, 104, 225, 182, 52, 25, 155, 108, 234, 93, 209, 234, 26, 195, 243, 200, 62, 165, 222, 46, 183, 199, 41, 0, 237, 229, 203, 110, 178, 107, 99, 138, 156, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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