Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0eb0cbd08fd4cb733ec4734f3ef75ed126f4d36a3328194c0db0e99a8a28a9

Tx prefix hash: 0fe045bf031a9e18fb6ee7d46918b9fc32671a4c185f88bed96956e770eaa3a0
Tx public key: b265dd2e49de3600058673ff367312295d835b97dc50ac614fa3f94b5a8cadbb
Timestamp: 1746275194 Timestamp [UTC]: 2025-05-03 12:26:34 Age [y:d:h:m:s]: 01:200:00:53:27
Block: 1274869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407047 RingCT/type: yes/0
Extra: 01b265dd2e49de3600058673ff367312295d835b97dc50ac614fa3f94b5a8cadbb02110000000a1f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf756e2314b42ac515dca5e6771ed7300c35cda88f59d16eec72d7f2246f1f2d 0.000600000000 1762170 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": 1274879, "vin": [ { "gen": { "height": 1274869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf756e2314b42ac515dca5e6771ed7300c35cda88f59d16eec72d7f2246f1f2d" } } ], "extra": [ 1, 178, 101, 221, 46, 73, 222, 54, 0, 5, 134, 115, 255, 54, 115, 18, 41, 93, 131, 91, 151, 220, 80, 172, 97, 79, 163, 249, 75, 90, 140, 173, 187, 2, 17, 0, 0, 0, 10, 31, 144, 81, 122, 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: