Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fdb8cf703c210a3fe45865d3f0ffc1ab8f1655c5818c2485e2e059a20a89a0

Tx prefix hash: 3523ec0539560a0807fd69ce310ef7cce78c46f1515e404d3a53931386685d7a
Tx public key: 6c819c5ab406b4a74585fb09e8dcc524c2acf8a79fdcbcc3fdafe30b1d53fbf4
Timestamp: 1756366099 Timestamp [UTC]: 2025-08-28 07:28:19 Age [y:d:h:m:s]: 00:258:21:22:28
Block: 1356125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177231 RingCT/type: yes/0
Extra: 016c819c5ab406b4a74585fb09e8dcc524c2acf8a79fdcbcc3fdafe30b1d53fbf4021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 50d4b96a71140be30a3c442bac5bd4cad7e18ee230cc9e464b28b421d064df44 0.000600000000 1844130 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": 1356135, "vin": [ { "gen": { "height": 1356125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50d4b96a71140be30a3c442bac5bd4cad7e18ee230cc9e464b28b421d064df44" } } ], "extra": [ 1, 108, 129, 156, 90, 180, 6, 180, 167, 69, 133, 251, 9, 232, 220, 197, 36, 194, 172, 248, 167, 159, 220, 188, 195, 253, 175, 227, 11, 29, 83, 251, 244, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: