Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3baa03d8f5a9879b1fbe60ce83a254ce3d9ef3276c57a137fa7e27a9a8305b

Tx prefix hash: 58ab45c1e14e21df948f92f800a1505158b07a577a67ec729202adc8546c6846
Tx public key: 4ee299c95126063c6418aa529db6e72da64b253f38e9bc3aadefc793b3cd175c
Timestamp: 1728912013 Timestamp [UTC]: 2024-10-14 13:20:13 Age [y:d:h:m:s]: 02:036:00:16:00
Block: 1131446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550478 RingCT/type: yes/0
Extra: 014ee299c95126063c6418aa529db6e72da64b253f38e9bc3aadefc793b3cd175c021100000004e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 845b7c62471aa4a69bc914e67016e9e16ebc4a3c5b98217c85b6c149eb9f88b3 0.000600000000 1614347 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": 1131456, "vin": [ { "gen": { "height": 1131446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "845b7c62471aa4a69bc914e67016e9e16ebc4a3c5b98217c85b6c149eb9f88b3" } } ], "extra": [ 1, 78, 226, 153, 201, 81, 38, 6, 60, 100, 24, 170, 82, 157, 182, 231, 45, 166, 75, 37, 63, 56, 233, 188, 58, 173, 239, 199, 147, 179, 205, 23, 92, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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: