Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a85f11faf6ea8326f86f97cfcb6f052215c35ce7effdb65068ebabc4c227865

Tx prefix hash: ac3f3c00367fce9c6b315c44cf682b0c3688402db56a15f6b3b64d95b47a3700
Tx public key: 9e5ab72326ec4eb82468818bdf4971d4461c8fa4ac2c20f9fc228767c02972bd
Timestamp: 1722544683 Timestamp [UCT]: 2024-08-01 20:38:03 Age [y:d:h:m:s]: 00:245:20:56:33
Block: 1078646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175627 RingCT/type: yes/0
Extra: 019e5ab72326ec4eb82468818bdf4971d4461c8fa4ac2c20f9fc228767c02972bd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bbea0a5892c0b83ec390a21f0fb6c8673eb8755f60e48ccb6d3a0c888f01ae6 0.600000000000 1551263 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": 1078656, "vin": [ { "gen": { "height": 1078646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bbea0a5892c0b83ec390a21f0fb6c8673eb8755f60e48ccb6d3a0c888f01ae6" } } ], "extra": [ 1, 158, 90, 183, 35, 38, 236, 78, 184, 36, 104, 129, 139, 223, 73, 113, 212, 70, 28, 143, 164, 172, 44, 32, 249, 252, 34, 135, 103, 192, 41, 114, 189, 2, 17, 0, 0, 0, 6, 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