Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a417b742f8ac58161411687a18f1d4112c326cf8f5f2da66f58b059fa4fa91ea

Tx prefix hash: e4207fddfa2628c6212f05888f7b7d879cdff9fc4355002dc1c2f8cfbab8bf07
Tx public key: 58c7f99572cc54dbb9ed945b908f10b263d8afc42a8f0d83410cc51b4cf7689e
Timestamp: 1741433576 Timestamp [UTC]: 2025-03-08 11:32:56 Age [y:d:h:m:s]: 01:258:05:20:39
Block: 1234794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448700 RingCT/type: yes/0
Extra: 0158c7f99572cc54dbb9ed945b908f10b263d8afc42a8f0d83410cc51b4cf7689e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 17a13665cf9ecd77dd984eb5ac4e860bfb1f12752f28630fd8a3e50c9eaed881 0.000600000000 1721729 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": 1234804, "vin": [ { "gen": { "height": 1234794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17a13665cf9ecd77dd984eb5ac4e860bfb1f12752f28630fd8a3e50c9eaed881" } } ], "extra": [ 1, 88, 199, 249, 149, 114, 204, 84, 219, 185, 237, 148, 91, 144, 143, 16, 178, 99, 216, 175, 196, 42, 143, 13, 131, 65, 12, 197, 27, 76, 247, 104, 158, 2, 17, 0, 0, 0, 3, 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: