Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f19fc622e0d07f53d8db923b776e85c6ec141670211bf3672f99247953f15fb7

Tx prefix hash: 84a29a536774eb4b78bf737a60b047115f55991eb1e16356f4b60600cbde68ee
Tx public key: 745fa8d94207e7ce596ea4741b7118f713c7a0c1cc6365fab37e1d36b821a5dd
Timestamp: 1735111787 Timestamp [UCT]: 2024-12-25 07:29:47 Age [y:d:h:m:s]: 00:094:01:41:49
Block: 1182745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66991 RingCT/type: yes/0
Extra: 01745fa8d94207e7ce596ea4741b7118f713c7a0c1cc6365fab37e1d36b821a5dd021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4db13c0185c813d8255e813833ea4df9936a78cd36f9510b414c1dc06dc04c2 0.600000000000 1669182 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": 1182755, "vin": [ { "gen": { "height": 1182745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4db13c0185c813d8255e813833ea4df9936a78cd36f9510b414c1dc06dc04c2" } } ], "extra": [ 1, 116, 95, 168, 217, 66, 7, 231, 206, 89, 110, 164, 116, 27, 113, 24, 247, 19, 199, 160, 193, 204, 99, 101, 250, 179, 126, 29, 54, 184, 33, 165, 221, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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