Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6971c31cb5087405e4ea188dc39a6100f28e1c8ce91e38b387cff1acd41e87f2

Tx prefix hash: a58b7bb8998533f44c9563e6f4b5959fa3f8175ecbe20dd3e0eedfb9c6897319
Tx public key: bc66a2b1b71306d4ae07dc9fa06e4d913fd4013b989fee5e49c6014b815623c9
Timestamp: 1773786592 Timestamp [UTC]: 2026-03-17 22:29:52 Age [y:d:h:m:s]: 00:241:21:34:57
Block: 1500069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178300 RingCT/type: yes/0
Extra: 01bc66a2b1b71306d4ae07dc9fa06e4d913fd4013b989fee5e49c6014b815623c9021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 73e01b1159c1d21cb392ead47770c6305d47073ccbc01eb999570ad5c54e1f10 0.000600000000 1989737 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": 1500079, "vin": [ { "gen": { "height": 1500069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73e01b1159c1d21cb392ead47770c6305d47073ccbc01eb999570ad5c54e1f10" } } ], "extra": [ 1, 188, 102, 162, 177, 183, 19, 6, 212, 174, 7, 220, 159, 160, 110, 77, 145, 63, 212, 1, 59, 152, 159, 238, 94, 73, 198, 1, 75, 129, 86, 35, 201, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: