Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6868f7c8d0f817849b78480f41ea06c3571fa90fd43a21c83c70bc171f88f2c1

Tx prefix hash: 3988ac44477929df1c7d6e370891a0d891bef8c3d8341f5ec974d207fa314a97
Tx public key: cef6547b2abd110ce7f8897944eec90415f0d7c1953f2bd1d1446528cf6519f0
Timestamp: 1741736736 Timestamp [UTC]: 2025-03-11 23:45:36 Age [y:d:h:m:s]: 01:251:16:58:23
Block: 1237300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443953 RingCT/type: yes/0
Extra: 01cef6547b2abd110ce7f8897944eec90415f0d7c1953f2bd1d1446528cf6519f00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6e2ea847bddc24d27e61f8b5063a8553df4eaf6da6d0cb03e004c64b10a4472f 0.000600000000 1724255 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": 1237310, "vin": [ { "gen": { "height": 1237300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2ea847bddc24d27e61f8b5063a8553df4eaf6da6d0cb03e004c64b10a4472f" } } ], "extra": [ 1, 206, 246, 84, 123, 42, 189, 17, 12, 231, 248, 137, 121, 68, 238, 201, 4, 21, 240, 215, 193, 149, 63, 43, 209, 209, 68, 101, 40, 207, 101, 25, 240, 2, 17, 0, 0, 0, 4, 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: