Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a18d952510634c069d4d36d2c8ee4bacfdd1218805f8934dbf1759dbd70b8a5

Tx prefix hash: 295099af9c94a5a2e4474b267a44df0e1301ab4e53361022fee18ea5ac19fd9b
Tx public key: 29ff57ab3d537f594370e7e747d7bb764f221e75cdc37e59f6fe70ec189ea297
Timestamp: 1766040723 Timestamp [UCT]: 2025-12-18 06:52:03 Age [y:d:h:m:s]: 00:005:08:49:03
Block: 1436121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3830 RingCT/type: yes/0
Extra: 0129ff57ab3d537f594370e7e747d7bb764f221e75cdc37e59f6fe70ec189ea2970211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9aa150db2c02d2c539bc5f07c15da7a1d36f17c63d38abd221d2c9d41a8cd2 0.600000000000 1924926 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": 1436131, "vin": [ { "gen": { "height": 1436121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9aa150db2c02d2c539bc5f07c15da7a1d36f17c63d38abd221d2c9d41a8cd2" } } ], "extra": [ 1, 41, 255, 87, 171, 61, 83, 127, 89, 67, 112, 231, 231, 71, 215, 187, 118, 79, 34, 30, 117, 205, 195, 126, 89, 246, 254, 112, 236, 24, 158, 162, 151, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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