Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5df22c26fa1eb7adb587b49b0d63fb0a59640c7062ea793132e75065222d9d

Tx prefix hash: c454a631cbdc531dd21b65912cc83773a085ff64b89f2da952087c1c45ed3cf2
Tx public key: b23f75083c5160f80b11e51229c611151f3e8a7c83014c4d443af03eb85e94a0
Timestamp: 1741491880 Timestamp [UTC]: 2025-03-09 03:44:40 Age [y:d:h:m:s]: 00:344:15:32:24
Block: 1235271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243972 RingCT/type: yes/0
Extra: 01b23f75083c5160f80b11e51229c611151f3e8a7c83014c4d443af03eb85e94a0021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80e7c56102512133c7e825bfe0f9188532dfba8de7af412825023f112009431a 0.000600000000 1722210 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": 1235281, "vin": [ { "gen": { "height": 1235271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80e7c56102512133c7e825bfe0f9188532dfba8de7af412825023f112009431a" } } ], "extra": [ 1, 178, 63, 117, 8, 60, 81, 96, 248, 11, 17, 229, 18, 41, 198, 17, 21, 31, 62, 138, 124, 131, 1, 76, 77, 68, 58, 240, 62, 184, 94, 148, 160, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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) | dinastycoin version: tesla-369