Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15bfa431ae2013f1fbf2257bd07bc0519bd7b2c765e3188ea97263ba5f3aa893

Tx prefix hash: 21e5ffef40eba054090333c0f57d39dd69b8302d3b8b6f644ead9eea9768abf9
Tx public key: 5e15e5d5dd72fdeb6b0365f42cb38a8411af685ee3f126f6e0bbe1d1976eef7e
Timestamp: 1726807735 Timestamp [UCT]: 2024-09-20 04:48:55 Age [y:d:h:m:s]: 00:250:22:59:52
Block: 1113994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179225 RingCT/type: yes/0
Extra: 015e15e5d5dd72fdeb6b0365f42cb38a8411af685ee3f126f6e0bbe1d1976eef7e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0449c5e4fbcf545c2438c17abfbc6edbb984833e1d9d4f8f64083fc03787667a 0.600000000000 1593791 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": 1114004, "vin": [ { "gen": { "height": 1113994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0449c5e4fbcf545c2438c17abfbc6edbb984833e1d9d4f8f64083fc03787667a" } } ], "extra": [ 1, 94, 21, 229, 213, 221, 114, 253, 235, 107, 3, 101, 244, 44, 179, 138, 132, 17, 175, 104, 94, 227, 241, 38, 246, 224, 187, 225, 209, 151, 110, 239, 126, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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