Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62430fb3ad78de2d755fcf312f5c40a7b8afbc3b74a930c202e9319c25e4227e

Tx prefix hash: d1f783463b8b695d620ea369dbefbe93b3274e88e57e5eb10e8ce06d94ff5ffd
Tx public key: 1190029b375c6defcf10e80546a21c4353103e43b211a8c46906a8c6679285ae
Timestamp: 1767360950 Timestamp [UTC]: 2026-01-02 13:35:50 Age [y:d:h:m:s]: 00:321:13:41:32
Block: 1447073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235284 RingCT/type: yes/0
Extra: 011190029b375c6defcf10e80546a21c4353103e43b211a8c46906a8c6679285ae02110000000b49d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2734146d4e5ad1e3aa20f62d87133c127b4d817f478b895eeb9bb6b1881bb9f 0.000600000000 1936031 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": 1447083, "vin": [ { "gen": { "height": 1447073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2734146d4e5ad1e3aa20f62d87133c127b4d817f478b895eeb9bb6b1881bb9f" } } ], "extra": [ 1, 17, 144, 2, 155, 55, 92, 109, 239, 207, 16, 232, 5, 70, 162, 28, 67, 83, 16, 62, 67, 178, 17, 168, 196, 105, 6, 168, 198, 103, 146, 133, 174, 2, 17, 0, 0, 0, 11, 73, 215, 62, 152, 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: