Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a2964de84702eb8484df8d6ca46e32e33534abb3b1c317bc99470a684ecb8a

Tx prefix hash: 55779441611ceee582e4ad4401d66f2db9672fe23311c60fd83cac625d7fdb57
Tx public key: ef41bf9487b7130a50be38b260d9ae09a4675bbf23b1ba34aed17a0c1df71d25
Timestamp: 1742023180 Timestamp [UTC]: 2025-03-15 07:19:40 Age [y:d:h:m:s]: 01:246:16:36:42
Block: 1239683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440324 RingCT/type: yes/0
Extra: 01ef41bf9487b7130a50be38b260d9ae09a4675bbf23b1ba34aed17a0c1df71d25021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 558d78d5839c7d824231cc574e019ae3b7243d713812ae073976e6efaa616172 0.000600000000 1726648 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": 1239693, "vin": [ { "gen": { "height": 1239683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558d78d5839c7d824231cc574e019ae3b7243d713812ae073976e6efaa616172" } } ], "extra": [ 1, 239, 65, 191, 148, 135, 183, 19, 10, 80, 190, 56, 178, 96, 217, 174, 9, 164, 103, 91, 191, 35, 177, 186, 52, 174, 209, 122, 12, 29, 247, 29, 37, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: