Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc8ff5a3b7c1d33592eb0479fd4ff2b576851472c90feb1e33594eceef632b4d

Tx prefix hash: f4a1bdc503faedc4c2d406f1af8e76794d6ac2c72d0407aae6978b2497d29f20
Tx public key: aa31a972e8800a94bcdf8049cf494a9eba903525c7f259625b56cd5d188430e5
Timestamp: 1729766508 Timestamp [UTC]: 2024-10-24 10:41:48 Age [y:d:h:m:s]: 02:028:19:49:13
Block: 1138487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545007 RingCT/type: yes/0
Extra: 01aa31a972e8800a94bcdf8049cf494a9eba903525c7f259625b56cd5d188430e50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000605780000 xmr

stealth address amount amount idx tag
00: 0ae3beaf3c542a0ddcd652decf6b38a0c83aa5154f8d1c40cd1ceab790838bdb 0.000605780000 1622166 of 0 -

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 dinastycoin-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": 1138497, "vin": [ { "gen": { "height": 1138487 } } ], "vout": [ { "amount": 605780000, "target": { "key": "0ae3beaf3c542a0ddcd652decf6b38a0c83aa5154f8d1c40cd1ceab790838bdb" } } ], "extra": [ 1, 170, 49, 169, 114, 232, 128, 10, 148, 188, 223, 128, 73, 207, 73, 74, 158, 186, 144, 53, 37, 199, 242, 89, 98, 91, 86, 205, 93, 24, 132, 48, 229, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: