Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab73b423cf575146ffd0983b8f31cc3fe27e75ef1c695c033707c35fb36f040

Tx prefix hash: e9696c4b54e5d9910f5c663961df57ee21b9983c2226cb096a52a0b104eea9e2
Tx public key: 6a84238673c23e989f46900eb3bdfd533d931a240eb31877544c41c267d88870
Timestamp: 1707771255 Timestamp [UTC]: 2024-02-12 20:54:15 Age [y:d:h:m:s]: 02:282:19:16:13
Block: 956169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727325 RingCT/type: yes/0
Extra: 016a84238673c23e989f46900eb3bdfd533d931a240eb31877544c41c267d888700211000000080011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 507f90d99ce21b3907b83179cf3da9f7dc28a1f1fbfd2c2cb2c7ee4eec80e262 0.000600000000 1415471 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": 956179, "vin": [ { "gen": { "height": 956169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507f90d99ce21b3907b83179cf3da9f7dc28a1f1fbfd2c2cb2c7ee4eec80e262" } } ], "extra": [ 1, 106, 132, 35, 134, 115, 194, 62, 152, 159, 70, 144, 14, 179, 189, 253, 83, 61, 147, 26, 36, 14, 179, 24, 119, 84, 76, 65, 194, 103, 216, 136, 112, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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: