Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8da2a15bc7261dbb12d45f110d0eb9990f1de3b0bbdb9a4aaea5b148a7d2de37

Tx prefix hash: 672a4e3ef4425add6ec1184081e5de17ad6966d26443ed8926ac9cb55cf5c146
Tx public key: b95f69a69aed4f29a3ad7767f1130883f809db0813536dea82d5f5068bf6c6e2
Timestamp: 1761096104 Timestamp [UCT]: 2025-10-22 01:21:44 Age [y:d:h:m:s]: 00:066:22:23:47
Block: 1395149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47924 RingCT/type: yes/0
Extra: 01b95f69a69aed4f29a3ad7767f1130883f809db0813536dea82d5f5068bf6c6e2021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b8b4850b45ee99837bf98714d7fe746f769d7d19e2dcef8000c08f9f221209c 0.600000000000 1883426 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": 1395159, "vin": [ { "gen": { "height": 1395149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b8b4850b45ee99837bf98714d7fe746f769d7d19e2dcef8000c08f9f221209c" } } ], "extra": [ 1, 185, 95, 105, 166, 154, 237, 79, 41, 163, 173, 119, 103, 241, 19, 8, 131, 248, 9, 219, 8, 19, 83, 109, 234, 130, 213, 245, 6, 139, 246, 198, 226, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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