Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2fb1e485681e9945cd61391e59d13c435633cf31f1b5abead2909508e6204da

Tx prefix hash: 1babfd0adfb7c772ad91069bf39fcb6f860075a723d630f5a84840b652ca72e1
Tx public key: 254f65e36ff96465f5a98b4c39a5f7d21ca270e78e08c6505234eece2ab7a830
Timestamp: 1712693734 Timestamp [UTC]: 2024-04-09 20:15:34 Age [y:d:h:m:s]: 02:226:12:00:11
Block: 996958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686536 RingCT/type: yes/0
Extra: 01254f65e36ff96465f5a98b4c39a5f7d21ca270e78e08c6505234eece2ab7a83002110000000559dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f1671d5a40f09c0bf18da494d393d18c9a9ef3bb1cc74225bc108e200f275cf6 0.000600000000 1457386 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": 996968, "vin": [ { "gen": { "height": 996958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1671d5a40f09c0bf18da494d393d18c9a9ef3bb1cc74225bc108e200f275cf6" } } ], "extra": [ 1, 37, 79, 101, 227, 111, 249, 100, 101, 245, 169, 139, 76, 57, 165, 247, 210, 28, 162, 112, 231, 142, 8, 198, 80, 82, 52, 238, 206, 42, 183, 168, 48, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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: