Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1bf23962b174cba0ac0200568e0a981e692eb6f2040f19ae0b69419d6a32fe8

Tx prefix hash: b6c6cda41c903363f217fdb5e3aabf6176f915ab78dd7e422020820392ef8ed3
Tx public key: e2b8290a0345d74c4ee8718089201433548b0b24545122bb5b581b18dfd835c1
Timestamp: 1767512439 Timestamp [UTC]: 2026-01-04 07:40:39 Age [y:d:h:m:s]: 00:043:06:29:19
Block: 1448326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30767 RingCT/type: yes/0
Extra: 01e2b8290a0345d74c4ee8718089201433548b0b24545122bb5b581b18dfd835c102110000000449d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4822848114499e9dce35b7b38f41ad04ce011d3535e3f7d7dc467e12cfa41a6c 0.000600000000 1937290 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": 1448336, "vin": [ { "gen": { "height": 1448326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4822848114499e9dce35b7b38f41ad04ce011d3535e3f7d7dc467e12cfa41a6c" } } ], "extra": [ 1, 226, 184, 41, 10, 3, 69, 215, 76, 78, 232, 113, 128, 137, 32, 20, 51, 84, 139, 11, 36, 84, 81, 34, 187, 91, 88, 27, 24, 223, 216, 53, 193, 2, 17, 0, 0, 0, 4, 73, 215, 62, 152, 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