Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e28e76fb0341528bce1cfe4d0c480ad517a0cdfbb705382a65b858b76eebf79

Tx prefix hash: bae58d7e1f72ffbcf2dd2cead75338b5b90839f18cf6eacff3b0fc4e1fe4c521
Tx public key: bf6234705d81fe1cc3bb3c8e3db4a2f0c17fb86d98d0ff0a4496993fb6a06f58
Timestamp: 1772835665 Timestamp [UTC]: 2026-03-06 22:21:05 Age [y:d:h:m:s]: 00:257:18:32:47
Block: 1492227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189799 RingCT/type: yes/0
Extra: 01bf6234705d81fe1cc3bb3c8e3db4a2f0c17fb86d98d0ff0a4496993fb6a06f5802110000000ef188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 68e5ce1be880c10aaf13a8c62646b9b9b96e26c2587519f93838eb75cadf63d4 0.000600000000 1981767 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": 1492237, "vin": [ { "gen": { "height": 1492227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e5ce1be880c10aaf13a8c62646b9b9b96e26c2587519f93838eb75cadf63d4" } } ], "extra": [ 1, 191, 98, 52, 112, 93, 129, 254, 28, 195, 187, 60, 142, 61, 180, 162, 240, 193, 127, 184, 109, 152, 208, 255, 10, 68, 150, 153, 63, 182, 160, 111, 88, 2, 17, 0, 0, 0, 14, 241, 136, 200, 168, 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: