Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bd00d7b88e86deaaa16adb7df099c0471900b35467931cb17a4abe53ab3d0a3

Tx prefix hash: 996d904d7560ad5cc7c2ef8191301613e0bb4dde74f6b12f07cec52d0e283876
Tx public key: 7778a9f30e385463bb469551f9b9e0f721f8f62e49ac4f7d165020f196f705ec
Timestamp: 1697130344 Timestamp [UCT]: 2023-10-12 17:05:44 Age [y:d:h:m:s]: 01:161:18:48:19
Block: 868167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376647 RingCT/type: yes/0
Extra: 017778a9f30e385463bb469551f9b9e0f721f8f62e49ac4f7d165020f196f705ec0211000000044b8f5122000000000000000000

1 output(s) for total of 0.815499442000 dcy

stealth address amount amount idx
00: 34d774c95842ddb9082d18b53dfe77803bdae2ca4a4670556914833d79573aea 0.815499442000 1322942 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": 868177, "vin": [ { "gen": { "height": 868167 } } ], "vout": [ { "amount": 815499442, "target": { "key": "34d774c95842ddb9082d18b53dfe77803bdae2ca4a4670556914833d79573aea" } } ], "extra": [ 1, 119, 120, 169, 243, 14, 56, 84, 99, 187, 70, 149, 81, 249, 185, 224, 247, 33, 248, 246, 46, 73, 172, 79, 125, 22, 80, 32, 241, 150, 247, 5, 236, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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