Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81d9b9b5aaadaee406aeae7ac8ca6fc2932c9574658adb632a59d1cd53d3dc9a

Tx prefix hash: 9c16c6969d65fd5781ac419ec6919bb78db7f317742f3bc304be4f941900786b
Tx public key: c69f89f8be35a9998ec112a3b8b61d602254c3cdd5870838e8f770a837409bcf
Timestamp: 1719692152 Timestamp [UTC]: 2024-06-29 20:15:52 Age [y:d:h:m:s]: 02:146:00:36:18
Block: 1054991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629159 RingCT/type: yes/0
Extra: 01c69f89f8be35a9998ec112a3b8b61d602254c3cdd5870838e8f770a837409bcf02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 69ac15e1cf4471b3d2b54d632985ec41f151046f35737d84bfd210f38dba2062 0.000600000000 1525382 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": 1055001, "vin": [ { "gen": { "height": 1054991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69ac15e1cf4471b3d2b54d632985ec41f151046f35737d84bfd210f38dba2062" } } ], "extra": [ 1, 198, 159, 137, 248, 190, 53, 169, 153, 142, 193, 18, 163, 184, 182, 29, 96, 34, 84, 195, 205, 213, 135, 8, 56, 232, 247, 112, 168, 55, 64, 155, 207, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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: