Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a063bd92165fec9e9b02180a76ddd5cb51caf2568c1030a58d01b3fa71b19a92

Tx prefix hash: 29f291c9623a94b791def5db577c672a2165aace2cce4d5f510d339a3f0e7cc8
Tx public key: 7188384f859cc11d11cd2b2d6991840aa58895632b37f44dba42b2ddcff2f694
Timestamp: 1721770319 Timestamp [UCT]: 2024-07-23 21:31:59 Age [y:d:h:m:s]: 01:108:01:59:44
Block: 1072225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335747 RingCT/type: yes/0
Extra: 017188384f859cc11d11cd2b2d6991840aa58895632b37f44dba42b2ddcff2f69402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25d30d1fb558072e0fa9bda42a69d7e5675f86a269c5df9e9117ae5d5243005c 0.600000000000 1544682 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 dinasty-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": 1072235, "vin": [ { "gen": { "height": 1072225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25d30d1fb558072e0fa9bda42a69d7e5675f86a269c5df9e9117ae5d5243005c" } } ], "extra": [ 1, 113, 136, 56, 79, 133, 156, 193, 29, 17, 205, 43, 45, 105, 145, 132, 10, 165, 136, 149, 99, 43, 55, 244, 77, 186, 66, 178, 221, 207, 242, 246, 148, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8