Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05ce406838bf86cf6720fcb7e32bb4fcb126426a24044e2b718dd6072b00f3b2

Tx prefix hash: bfb3e6b59801e7487b1a9f7e312aa671a30a740729c4b5ee7f25e7aac191aed7
Tx public key: fd759b494c2eda400780ac0e0547e96c42b6073f9706b46cd9c94513f85c93c6
Timestamp: 1736568772 Timestamp [UTC]: 2025-01-11 04:12:52 Age [y:d:h:m:s]: 01:123:00:14:35
Block: 1194777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338570 RingCT/type: yes/0
Extra: 01fd759b494c2eda400780ac0e0547e96c42b6073f9706b46cd9c94513f85c93c6021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 730e4413be6f009af1266d834f3f5647804ce5587d8aeb35eff1b3c55da5631c 0.000600000000 1681354 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": 1194787, "vin": [ { "gen": { "height": 1194777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "730e4413be6f009af1266d834f3f5647804ce5587d8aeb35eff1b3c55da5631c" } } ], "extra": [ 1, 253, 117, 155, 73, 76, 46, 218, 64, 7, 128, 172, 14, 5, 71, 233, 108, 66, 182, 7, 63, 151, 6, 180, 108, 217, 201, 69, 19, 248, 92, 147, 198, 2, 17, 0, 0, 0, 2, 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: