Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed6d3c0df69e66db1c34daefad73e1837ae8b455911342ca932ecd49df80ef76

Tx prefix hash: f4d8e22aa26d3f974c655e95176a7e42b0234a671588979291fa352a3ba6bb7c
Tx public key: ba7e6e67b4108c0782b407a4fb17f9800e4f24a4895e10a4e95c2db52576ad7d
Timestamp: 1774783172 Timestamp [UTC]: 2026-03-29 11:19:32 Age [y:d:h:m:s]: 00:234:06:31:58
Block: 1508329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172961 RingCT/type: yes/0
Extra: 01ba7e6e67b4108c0782b407a4fb17f9800e4f24a4895e10a4e95c2db52576ad7d021100000011f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a6e52c04765cd33131ae5ff680bcd94c20d1e492988e858a3cbe81739722948 0.000600000000 1998081 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": 1508339, "vin": [ { "gen": { "height": 1508329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6e52c04765cd33131ae5ff680bcd94c20d1e492988e858a3cbe81739722948" } } ], "extra": [ 1, 186, 126, 110, 103, 180, 16, 140, 7, 130, 180, 7, 164, 251, 23, 249, 128, 14, 79, 36, 164, 137, 94, 16, 164, 233, 92, 45, 181, 37, 118, 173, 125, 2, 17, 0, 0, 0, 17, 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: