Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0c321b9666f7965edada8c577ab8cfa3b9c6356c9cc5dc82be4d073effd2c5

Tx prefix hash: 06383ab66ce9dad3df201e47abc35e9d9fb8aeea2ee690212d1f050559b8b4ff
Tx public key: f2df8a6b727f8047460691e2a0e47f47d5da6f3d88e65a28d0608ad474aa39e1
Timestamp: 1742342202 Timestamp [UTC]: 2025-03-18 23:56:42 Age [y:d:h:m:s]: 01:247:05:49:56
Block: 1242329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440875 RingCT/type: yes/0
Extra: 01f2df8a6b727f8047460691e2a0e47f47d5da6f3d88e65a28d0608ad474aa39e10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 046dcb237d4eda6b267f3d0c1af97946cb96ebde2920972df174fe49675577a7 0.000600000000 1729302 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": 1242339, "vin": [ { "gen": { "height": 1242329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "046dcb237d4eda6b267f3d0c1af97946cb96ebde2920972df174fe49675577a7" } } ], "extra": [ 1, 242, 223, 138, 107, 114, 127, 128, 71, 70, 6, 145, 226, 160, 228, 127, 71, 213, 218, 111, 61, 136, 230, 90, 40, 208, 96, 138, 212, 116, 170, 57, 225, 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: