Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 152c4ed2b57c5c4c27f1fb304cf15ee0d38469b3b2bc73f1c8add86a1dc0083d

Tx prefix hash: a85c25172dccd0290ac2f002512ecd31415f62b6765e42c1c9126615fd75be00
Tx public key: 8e8d9b75ff2164d8848115f89f47fe639abaad12fae991c79f7313d8a694c952
Timestamp: 1745524267 Timestamp [UTC]: 2025-04-24 19:51:07 Age [y:d:h:m:s]: 01:087:07:24:01
Block: 1268650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314464 RingCT/type: yes/0
Extra: 018e8d9b75ff2164d8848115f89f47fe639abaad12fae991c79f7313d8a694c952021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c082c93b4e0d9aad7cdfb21f2fe0bd79edb837c83e7e20b825e3fa0ae353cf6c 0.000600000000 1755881 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 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": 1268660, "vin": [ { "gen": { "height": 1268650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c082c93b4e0d9aad7cdfb21f2fe0bd79edb837c83e7e20b825e3fa0ae353cf6c" } } ], "extra": [ 1, 142, 141, 155, 117, 255, 33, 100, 216, 132, 129, 21, 248, 159, 71, 254, 99, 154, 186, 173, 18, 250, 233, 145, 199, 159, 115, 19, 216, 166, 148, 201, 82, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: