Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64458d14e80641a705796f988b4e1c15ac49c9628d2a7781252c54fa19d583ec

Tx prefix hash: 208641127a18a1dc17c0a46a26aa17a475a865f27237e3c7641850f87f80bfe0
Tx public key: 9b15724ba77c1027c913dfe3ae2a73ea250e5faebb09b342024e85d2b162890c
Timestamp: 1734804608 Timestamp [UCT]: 2024-12-21 18:10:08 Age [y:d:h:m:s]: 00:089:12:17:55
Block: 1180203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63742 RingCT/type: yes/0
Extra: 019b15724ba77c1027c913dfe3ae2a73ea250e5faebb09b342024e85d2b162890c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e30f1dc29c6bd06e90195c4f1be352dcf36c12de48a58078136c7668f051ed6 0.600000000000 1666612 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": 1180213, "vin": [ { "gen": { "height": 1180203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e30f1dc29c6bd06e90195c4f1be352dcf36c12de48a58078136c7668f051ed6" } } ], "extra": [ 1, 155, 21, 114, 75, 167, 124, 16, 39, 201, 19, 223, 227, 174, 42, 115, 234, 37, 14, 95, 174, 187, 9, 179, 66, 2, 78, 133, 210, 177, 98, 137, 12, 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