Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82c522377d28146abe3f8e381b6fbd11fcfb3da7863f7dd314fb4ce9b05b0c1

Tx prefix hash: 15d220025a3bdf24e6921362cdf528ae560d03d2adc6c7d802c56a0a073fe36d
Tx public key: 69c347d956dabff706d25401497b0b6ffa26e8b9d7adc9eb1cdca68bdabf8f87
Timestamp: 1745396642 Timestamp [UCT]: 2025-04-23 08:24:02 Age [y:d:h:m:s]: 00:255:13:22:12
Block: 1267591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180440 RingCT/type: yes/0
Extra: 0169c347d956dabff706d25401497b0b6ffa26e8b9d7adc9eb1cdca68bdabf8f870211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9830d6de787d70d5a8bef78929fef737a39fecb31dda45d018989653f0dc1361 0.600000000000 1754820 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": 1267601, "vin": [ { "gen": { "height": 1267591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9830d6de787d70d5a8bef78929fef737a39fecb31dda45d018989653f0dc1361" } } ], "extra": [ 1, 105, 195, 71, 217, 86, 218, 191, 247, 6, 210, 84, 1, 73, 123, 11, 111, 250, 38, 232, 185, 215, 173, 201, 235, 28, 220, 166, 139, 218, 191, 143, 135, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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