Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ba26d974e9649c06b0d2aeb85f6ff807f6fc807da3b74ae0024140182c2612e

Tx prefix hash: e18f324cf721ddfefaef9f308a46c1712a7ea552403f145dc08b1201a4e2b2b8
Tx public key: 094b9365b3f562cf1e2ef772016f10b25293fe611c70e743c494e70ef6b0bc52
Timestamp: 1708284767 Timestamp [UTC]: 2024-02-18 19:32:47 Age [y:d:h:m:s]: 02:274:14:49:23
Block: 960434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721381 RingCT/type: yes/0
Extra: 01094b9365b3f562cf1e2ef772016f10b25293fe611c70e743c494e70ef6b0bc520211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e56a17e8736d17d5c4a1015d136fe9ae38bd4b80912f29d161eea89a6eddf27f 0.000600000000 1419999 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": 960444, "vin": [ { "gen": { "height": 960434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e56a17e8736d17d5c4a1015d136fe9ae38bd4b80912f29d161eea89a6eddf27f" } } ], "extra": [ 1, 9, 75, 147, 101, 179, 245, 98, 207, 30, 46, 247, 114, 1, 111, 16, 178, 82, 147, 254, 97, 28, 112, 231, 67, 196, 148, 231, 14, 246, 176, 188, 82, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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: