Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07d71957ad62f9c6db2d83bdf96efd9a7bce0cc25331c3863765db6b3be76b3a

Tx prefix hash: 0911f4de0d6c7c210b047ac0d333c987994cac77ccb207358ea1b57056987bf6
Tx public key: 55d87d868e367ff1a357b3f149868f05b9ffe16c043b1d1472d3986345fca077
Timestamp: 1734511125 Timestamp [UCT]: 2024-12-18 08:38:45 Age [y:d:h:m:s]: 00:103:20:07:30
Block: 1177768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73983 RingCT/type: yes/0
Extra: 0155d87d868e367ff1a357b3f149868f05b9ffe16c043b1d1472d3986345fca0770211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5e6d688e8f6fd84523f11e42a5b39db32ab0761ba5c81b619676f83d7eb3d3b 0.600000000000 1664145 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": 1177778, "vin": [ { "gen": { "height": 1177768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5e6d688e8f6fd84523f11e42a5b39db32ab0761ba5c81b619676f83d7eb3d3b" } } ], "extra": [ 1, 85, 216, 125, 134, 142, 54, 127, 241, 163, 87, 179, 241, 73, 134, 143, 5, 185, 255, 225, 108, 4, 59, 29, 20, 114, 211, 152, 99, 69, 252, 160, 119, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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