Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbb9c2588e16c45e28b26ea8954d197708bedfa02a5770c542e8ebdbe615a40

Tx prefix hash: d14401500057dc61f4508871c41e5f4dae1950c3ca9b494f0f735fc333a60d5d
Tx public key: 87a7a68166e5a2fb86477ab1853d04d60ac7851eddc233e00fb43417d6d8a2b9
Timestamp: 1767532471 Timestamp [UTC]: 2026-01-04 13:14:31 Age [y:d:h:m:s]: 00:042:14:12:13
Block: 1448495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 30288 RingCT/type: yes/0
Extra: 0187a7a68166e5a2fb86477ab1853d04d60ac7851eddc233e00fb43417d6d8a2b9020900000008f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 013a32f0b90a8b114fd41094a34e96249307d3a2477583c42e87f91e58bc8023 0.000600000000 1937463 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": 1448505, "vin": [ { "gen": { "height": 1448495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013a32f0b90a8b114fd41094a34e96249307d3a2477583c42e87f91e58bc8023" } } ], "extra": [ 1, 135, 167, 166, 129, 102, 229, 162, 251, 134, 71, 122, 177, 133, 61, 4, 214, 10, 199, 133, 30, 221, 194, 51, 224, 15, 180, 52, 23, 214, 216, 162, 185, 2, 9, 0, 0, 0, 8, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369