Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 159aa8ff33cdae990315a3a3b0a2142f700ccd10fa969cbc4c9189dac938a63a

Tx prefix hash: f95537e1a8827fc2bcf689eea8796654fb91b69134bce4d57b0e2cf82341f0e7
Tx public key: 31f3dc6b2813da50efd5ff243d011a1556d04cd134200aee3e4aa65396e75c68
Timestamp: 1727817249 Timestamp [UCT]: 2024-10-01 21:14:09 Age [y:d:h:m:s]: 00:213:22:35:48
Block: 1122366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152716 RingCT/type: yes/0
Extra: 0131f3dc6b2813da50efd5ff243d011a1556d04cd134200aee3e4aa65396e75c6802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17179bb650df91431ce862ac5b9e2da002c7dc2ecd54af6f4d6703f7c77febcc 0.600000000000 1604791 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": 1122376, "vin": [ { "gen": { "height": 1122366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17179bb650df91431ce862ac5b9e2da002c7dc2ecd54af6f4d6703f7c77febcc" } } ], "extra": [ 1, 49, 243, 220, 107, 40, 19, 218, 80, 239, 213, 255, 36, 61, 1, 26, 21, 86, 208, 76, 209, 52, 32, 10, 238, 62, 74, 166, 83, 150, 231, 92, 104, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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