Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4576dd0952d3e54fffe0df8b834a702734d567c2189b0c9e80af91fb58be5f

Tx prefix hash: edbe55836d23d64fade85f0416d1b9d32205a52d987736f2637fc4bc97b3a235
Tx public key: f3d8e3dcbd3d21a40bc73cea26db21b678816ae0465f2bc5d4ffb2b9828f25e2
Timestamp: 1742782094 Timestamp [UTC]: 2025-03-24 02:08:14 Age [y:d:h:m:s]: 01:047:17:14:06
Block: 1245937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285355 RingCT/type: yes/0
Extra: 01f3d8e3dcbd3d21a40bc73cea26db21b678816ae0465f2bc5d4ffb2b9828f25e2021100000004c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97ae9ef6eabb6cdabf4703f1a6e1d2ddd4a67ba0653eb1a4a0315562375f8ce3 0.000600000000 1732932 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": 1245947, "vin": [ { "gen": { "height": 1245937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97ae9ef6eabb6cdabf4703f1a6e1d2ddd4a67ba0653eb1a4a0315562375f8ce3" } } ], "extra": [ 1, 243, 216, 227, 220, 189, 61, 33, 164, 11, 199, 60, 234, 38, 219, 33, 182, 120, 129, 106, 224, 70, 95, 43, 197, 212, 255, 178, 185, 130, 143, 37, 226, 2, 17, 0, 0, 0, 4, 198, 116, 9, 88, 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: