Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e7b719c85a11ef4b81603159b78de76905616475bb932d1f199a986536b1ae

Tx prefix hash: 39445b922fcb4e23dcd98d9d1d24810979e2d821ec319424d1cf827a32fa9280
Tx public key: c47cb4c3d24f855c90caf2bd99d18bf22c3cf8faf756bbc1dd2aaf75e4618bb0
Timestamp: 1731363775 Timestamp [UCT]: 2024-11-11 22:22:55 Age [y:d:h:m:s]: 00:363:05:43:11
Block: 1151672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257157 RingCT/type: yes/0
Extra: 01c47cb4c3d24f855c90caf2bd99d18bf22c3cf8faf756bbc1dd2aaf75e4618bb00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8851ae18a8137d543ac605adeeefb85bb79ef8a4d4151fa5bd8d6518395edb5 0.600000000000 1637245 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": 1151682, "vin": [ { "gen": { "height": 1151672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8851ae18a8137d543ac605adeeefb85bb79ef8a4d4151fa5bd8d6518395edb5" } } ], "extra": [ 1, 196, 124, 180, 195, 210, 79, 133, 92, 144, 202, 242, 189, 153, 209, 139, 242, 44, 60, 248, 250, 247, 86, 187, 193, 221, 42, 175, 117, 228, 97, 139, 176, 2, 17, 0, 0, 0, 2, 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