Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da9a48d2a4b15d60e0582f631e7961e8e70a785c0cf675dea06782ccbf4d9134

Tx prefix hash: 39f06e78c6d82171b934a00d63550e4fef27f2a20fac0fac1cb8d63f64923107
Tx public key: d6a7f0bb3b21ef4d66aed024dcec920b706f212bbb8c30f9fcf25059df8ef5a1
Timestamp: 1648319191 Timestamp [UCT]: 2022-03-26 18:26:31 Age [y:d:h:m:s]: 02:363:09:57:51
Block: 466950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779059 RingCT/type: yes/0
Extra: 01d6a7f0bb3b21ef4d66aed024dcec920b706f212bbb8c30f9fcf25059df8ef5a10211000000014da16a3a000000000000000000

1 output(s) for total of 17.410091908000 dcy

stealth address amount amount idx
00: bf7bf8087ef28f19e4768e8b77940992c57053d74cab888d4ac894d138caa210 17.410091908000 885359 of 0

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": 466960, "vin": [ { "gen": { "height": 466950 } } ], "vout": [ { "amount": 17410091908, "target": { "key": "bf7bf8087ef28f19e4768e8b77940992c57053d74cab888d4ac894d138caa210" } } ], "extra": [ 1, 214, 167, 240, 187, 59, 33, 239, 77, 102, 174, 208, 36, 220, 236, 146, 11, 112, 111, 33, 43, 187, 140, 48, 249, 252, 242, 80, 89, 223, 142, 245, 161, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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