Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ea32e2ea2856307f1f421e78b740c1473b4e80dd05c5001cde7f3558a5aa1bb

Tx prefix hash: 8bf0a56206098942344fc6d09ff102091173ed4d2cdbdb17b63fcd745ed5bb29
Tx public key: 52dcef015ec9bbf7ec7c31689d8d8a3250a3a9e1c25b859b5f194e9fabe58574
Timestamp: 1736890635 Timestamp [UCT]: 2025-01-14 21:37:15 Age [y:d:h:m:s]: 00:157:16:18:38
Block: 1197434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112361 RingCT/type: yes/0
Extra: 0152dcef015ec9bbf7ec7c31689d8d8a3250a3a9e1c25b859b5f194e9fabe58574021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5193ce3af4a8647b403780258aade66768e9bff2e34729d5b92598b90c49297a 0.600000000000 1684041 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": 1197444, "vin": [ { "gen": { "height": 1197434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5193ce3af4a8647b403780258aade66768e9bff2e34729d5b92598b90c49297a" } } ], "extra": [ 1, 82, 220, 239, 1, 94, 201, 187, 247, 236, 124, 49, 104, 157, 141, 138, 50, 80, 163, 169, 225, 194, 91, 133, 155, 95, 25, 78, 159, 171, 229, 133, 116, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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