Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a1fa931864664b0bf8b9485e6c1178a5a77476e92d90fad9df22e25bf5cabcd

Tx prefix hash: fb86d3b13f36ec4477a8459f563faa3c457a25aa7146fd137c3c84dd3895f9d0
Tx public key: 9a8e0bd1192c459e02e42f427648e9d6cff0d3b44872beeab1d826c2fd5425b1
Timestamp: 1708287142 Timestamp [UTC]: 2024-02-18 20:12:22 Age [y:d:h:m:s]: 02:274:20:53:06
Block: 960453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721578 RingCT/type: yes/0
Extra: 019a8e0bd1192c459e02e42f427648e9d6cff0d3b44872beeab1d826c2fd5425b10211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 34eaffd0e6db619ba3f26174eebc25a2b1c72f9198919347bd83217e15364a54 0.000600000000 1420018 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": 960463, "vin": [ { "gen": { "height": 960453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34eaffd0e6db619ba3f26174eebc25a2b1c72f9198919347bd83217e15364a54" } } ], "extra": [ 1, 154, 142, 11, 209, 25, 44, 69, 158, 2, 228, 47, 66, 118, 72, 233, 214, 207, 240, 211, 180, 72, 114, 190, 234, 177, 216, 38, 194, 253, 84, 37, 177, 2, 17, 0, 0, 0, 1, 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: