Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b5a7a862f7c807d58c64c6fe23cccd2b66de51f6ccbf93c9a8e5c502a5a7d48

Tx prefix hash: b106460f2dea366d595fd5a4cd09f8d1ca8bf6e7a6e048a2fd70e28c8c55f340
Tx public key: 6fe7c3af6134f7ef2aca48fd3f9113e8bbad315086167bb65b443bdc7adfdfb4
Timestamp: 1713444744 Timestamp [UCT]: 2024-04-18 12:52:24 Age [y:d:h:m:s]: 00:312:17:05:31
Block: 1003193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223542 RingCT/type: yes/0
Extra: 016fe7c3af6134f7ef2aca48fd3f9113e8bbad315086167bb65b443bdc7adfdfb402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 359e2bb5c2b071bb7c81a586a77efd9b01d915f9cf71c27aa413f480d1577358 0.600000000000 1463723 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": 1003203, "vin": [ { "gen": { "height": 1003193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "359e2bb5c2b071bb7c81a586a77efd9b01d915f9cf71c27aa413f480d1577358" } } ], "extra": [ 1, 111, 231, 195, 175, 97, 52, 247, 239, 42, 202, 72, 253, 63, 145, 19, 232, 187, 173, 49, 80, 134, 22, 123, 182, 91, 68, 59, 220, 122, 223, 223, 180, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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