Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed65ca54fd89934662518d426c75a89e78460abb2bc04a3eaa454825dd7f47cb

Tx prefix hash: b5713c1349b025b47fd038fe88f9ee8ad39287df5683f7c34a2447ebc0f7f6fc
Tx public key: 807a2b43db61b8e3fe73a0f1cb50c6f91104425113d81c552caf206cf7c11774
Timestamp: 1733508127 Timestamp [UTC]: 2024-12-06 18:02:07 Age [y:d:h:m:s]: 01:161:06:15:09
Block: 1169446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366035 RingCT/type: yes/0
Extra: 01807a2b43db61b8e3fe73a0f1cb50c6f91104425113d81c552caf206cf7c117740211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf10b8b1ac4ad70c0e77c0b27a626bf318402d32a2718c3e6d710d54ac047f95 0.000600000000 1655163 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": 1169456, "vin": [ { "gen": { "height": 1169446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf10b8b1ac4ad70c0e77c0b27a626bf318402d32a2718c3e6d710d54ac047f95" } } ], "extra": [ 1, 128, 122, 43, 67, 219, 97, 184, 227, 254, 115, 160, 241, 203, 80, 198, 249, 17, 4, 66, 81, 19, 216, 28, 85, 44, 175, 32, 108, 247, 193, 23, 116, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: