Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ccee31fa1ade6d06e0f07504c82f5e58a71f4e0f489fbc5a66b2e7ceecff8ca

Tx prefix hash: c07ea3e9f5138348b5077fd71d46aaaf7695cfe8859f11fc9377db8e781225a8
Tx public key: 8ecd37ea67484a93c911c1d2e5b6f3d7408de5b7cff209d0954003a67a74ab4d
Timestamp: 1773562968 Timestamp [UTC]: 2026-03-15 08:22:48 Age [y:d:h:m:s]: 00:243:20:56:47
Block: 1498242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179673 RingCT/type: yes/0
Extra: 018ecd37ea67484a93c911c1d2e5b6f3d7408de5b7cff209d0954003a67a74ab4d021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb1bd3eb87a214099c1fc8e5e91ae161a13ef8553fac312c28abe176bbbcabb2 0.000600000000 1987888 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": 1498252, "vin": [ { "gen": { "height": 1498242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb1bd3eb87a214099c1fc8e5e91ae161a13ef8553fac312c28abe176bbbcabb2" } } ], "extra": [ 1, 142, 205, 55, 234, 103, 72, 74, 147, 201, 17, 193, 210, 229, 182, 243, 215, 64, 141, 229, 183, 207, 242, 9, 208, 149, 64, 3, 166, 122, 116, 171, 77, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: