Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa32474832550e8af924413a955cac56fcc6a11fb82a4bf67e42bfdf767ca70

Tx prefix hash: c4207009553737b8e581d25ccd99068fcb09a93d87a7e425948b8ed4eda1e4c8
Tx public key: 9de9aedc6530efe1c99ba99220419b1d6ebdaaf4af924b840f14e3e7b06636ac
Timestamp: 1750722058 Timestamp [UCT]: 2025-06-23 23:40:58 Age [y:d:h:m:s]: 00:150:08:04:26
Block: 1311436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105364 RingCT/type: yes/0
Extra: 019de9aedc6530efe1c99ba99220419b1d6ebdaaf4af924b840f14e3e7b06636ac02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d341f28c02f1438ac2ef4e80e31d5236b798e0f10f2d957fbcd9815e2092ab2 0.600000000000 1799063 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": 1311446, "vin": [ { "gen": { "height": 1311436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d341f28c02f1438ac2ef4e80e31d5236b798e0f10f2d957fbcd9815e2092ab2" } } ], "extra": [ 1, 157, 233, 174, 220, 101, 48, 239, 225, 201, 155, 169, 146, 32, 65, 155, 29, 110, 189, 170, 244, 175, 146, 75, 132, 15, 20, 227, 231, 176, 102, 54, 172, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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