Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544b20233b644c7127fe242d84dd0e986b7fd2a090f9b45972bc1448aeddfd2c

Tx prefix hash: ea560e62034fe58a3336a328e26343df44e22f09c9f9008488ca5b28785889cc
Tx public key: 723b33a34d104f02044eb68b8250a66ec97723c11b8474a9f2aa66ef094398bd
Timestamp: 1750365402 Timestamp [UTC]: 2025-06-19 20:36:42 Age [y:d:h:m:s]: 00:330:06:15:07
Block: 1308591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226224 RingCT/type: yes/0
Extra: 01723b33a34d104f02044eb68b8250a66ec97723c11b8474a9f2aa66ef094398bd02110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3dad8a7573441ee5d1e012eb7fa3aa1835a0fca862d946b5d722a76a5bbb2a39 0.000600000000 1796204 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": 1308601, "vin": [ { "gen": { "height": 1308591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dad8a7573441ee5d1e012eb7fa3aa1835a0fca862d946b5d722a76a5bbb2a39" } } ], "extra": [ 1, 114, 59, 51, 163, 77, 16, 79, 2, 4, 78, 182, 139, 130, 80, 166, 110, 201, 119, 35, 193, 27, 132, 116, 169, 242, 170, 102, 239, 9, 67, 152, 189, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: