Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad55baa60ca92c94ea6032467abcd5bdc41d89b8365e9066cfcc7793ef6dcc6c

Tx prefix hash: 471cb1c347203423fcefdd34e355f1473cede6ff527c94ac82b9b9ddea1a202e
Tx public key: 3be76f5881531489330e219cd2deb529b089b55e48c5b4790d51a445ece4ec2e
Timestamp: 1771834365 Timestamp [UTC]: 2026-02-23 08:12:45 Age [y:d:h:m:s]: 00:265:09:30:22
Block: 1483940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195115 RingCT/type: yes/0
Extra: 013be76f5881531489330e219cd2deb529b089b55e48c5b4790d51a445ece4ec2e021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 165e29c39e37e00c0794d4edfaa4b9600a870e141018aff4b919dc6a514b0b57 0.000600000000 1973352 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": 1483950, "vin": [ { "gen": { "height": 1483940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165e29c39e37e00c0794d4edfaa4b9600a870e141018aff4b919dc6a514b0b57" } } ], "extra": [ 1, 59, 231, 111, 88, 129, 83, 20, 137, 51, 14, 33, 156, 210, 222, 181, 41, 176, 137, 181, 94, 72, 197, 180, 121, 13, 81, 164, 69, 236, 228, 236, 46, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: