Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5825367b2a2417b5ebd6f95d4cc0da1bef2646c9720b98f2f5400aba146119c

Tx prefix hash: e4950decad293a3cd9791a518a3c877831b956798a073f93d0b5737ec5179e99
Tx public key: e728a886f7b9e6e6a67c8b6f6bb0a7fd1655cdb72154b5c6a65ac323fbd7750f
Timestamp: 1704488969 Timestamp [UTC]: 2024-01-05 21:09:29 Age [y:d:h:m:s]: 02:134:12:05:31
Block: 928941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609213 RingCT/type: yes/0
Extra: 01e728a886f7b9e6e6a67c8b6f6bb0a7fd1655cdb72154b5c6a65ac323fbd7750f0211000000040011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4ca39ca2e5ee45cfb3acf61e0b39914188f2e33a5078aa7be0cc99480410cce1 0.000600000000 1386807 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": 928951, "vin": [ { "gen": { "height": 928941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ca39ca2e5ee45cfb3acf61e0b39914188f2e33a5078aa7be0cc99480410cce1" } } ], "extra": [ 1, 231, 40, 168, 134, 247, 185, 230, 230, 166, 124, 139, 111, 107, 176, 167, 253, 22, 85, 205, 183, 33, 84, 181, 198, 166, 90, 195, 35, 251, 215, 117, 15, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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: