Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e9cf6c6d90ac9abe6d5f458ed784f3feaadba161f545d07ac0df7021ffac98

Tx prefix hash: 0bb6076801c9e0f3deee1d069bbb4a4e9c5e5ee1528bacacad6f394e3ed89cb3
Tx public key: 80affb46da2160423181a28f89921f0231e9669d9fa9e14141c49ef9a1c1bf35
Timestamp: 1742132494 Timestamp [UTC]: 2025-03-16 13:41:34 Age [y:d:h:m:s]: 01:249:18:26:54
Block: 1240598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442673 RingCT/type: yes/0
Extra: 0180affb46da2160423181a28f89921f0231e9669d9fa9e14141c49ef9a1c1bf350211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 274cfdeeb04aed4b995e26e7c2aaa22642854f1970598ec7b63e7850513ca409 0.000600000000 1727571 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": 1240608, "vin": [ { "gen": { "height": 1240598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "274cfdeeb04aed4b995e26e7c2aaa22642854f1970598ec7b63e7850513ca409" } } ], "extra": [ 1, 128, 175, 251, 70, 218, 33, 96, 66, 49, 129, 162, 143, 137, 146, 31, 2, 49, 233, 102, 157, 159, 169, 225, 65, 65, 196, 158, 249, 161, 193, 191, 53, 2, 17, 0, 0, 0, 2, 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: