Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22b16dbd14d5c4d240572238554c92a65167cb673a1aaa5b35ee5f94166a3618

Tx prefix hash: 3ce1e32bf96d95279604d63d374317ca2c8cad624f789fc62d47df7baf5e98d1
Tx public key: 2b5f2d5543350c1ea922cc48e56832090f2a645da98330ad6f2d7ffe45dd0a86
Timestamp: 1746163693 Timestamp [UTC]: 2025-05-02 05:28:13 Age [y:d:h:m:s]: 00:277:05:30:41
Block: 1273940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195783 RingCT/type: yes/0
Extra: 012b5f2d5543350c1ea922cc48e56832090f2a645da98330ad6f2d7ffe45dd0a8602110000000301491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9af66c76719f5911b8b41c1dd9b1c33d3ec81d69d136fb04190e9a6d3d147616 0.000600000000 1761227 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": 1273950, "vin": [ { "gen": { "height": 1273940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9af66c76719f5911b8b41c1dd9b1c33d3ec81d69d136fb04190e9a6d3d147616" } } ], "extra": [ 1, 43, 95, 45, 85, 67, 53, 12, 30, 169, 34, 204, 72, 229, 104, 50, 9, 15, 42, 100, 93, 169, 131, 48, 173, 111, 45, 127, 254, 69, 221, 10, 134, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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