Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7f7df77431ccbddc3b314d72f3104d8b3d978cfb4327eff75d61c370081c88

Tx prefix hash: 74b0cd507d03d44dbce82b14e565b18e0d31bf5cf78342868178d9d21c4b94a6
Tx public key: f924af2fa9a499b59d80d3be40a37518e622c4173842cce9612a891c4af6e798
Timestamp: 1742025126 Timestamp [UTC]: 2025-03-15 07:52:06 Age [y:d:h:m:s]: 01:081:19:35:03
Block: 1239705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311878 RingCT/type: yes/0
Extra: 01f924af2fa9a499b59d80d3be40a37518e622c4173842cce9612a891c4af6e798021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: af92a1ce6536effeaf3ba2c98ce62d97cd0b9325d17c822e905eb28d2e78e2c9 0.000600000000 1726670 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": 1239715, "vin": [ { "gen": { "height": 1239705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af92a1ce6536effeaf3ba2c98ce62d97cd0b9325d17c822e905eb28d2e78e2c9" } } ], "extra": [ 1, 249, 36, 175, 47, 169, 164, 153, 181, 157, 128, 211, 190, 64, 163, 117, 24, 230, 34, 196, 23, 56, 66, 204, 233, 97, 42, 137, 28, 74, 246, 231, 152, 2, 17, 0, 0, 0, 5, 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: