Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8f75419d6a60e4fb8b7c789cca8ce5dd26415a175d66e9c5169712e9586d06

Tx prefix hash: 0558afe100abcf87b5f52104190f9ad36f9561a28f8087334ad07144ee1a6353
Tx public key: af9a5baaa9cfc8d8a5893eff23d7d4fa859b2b69c5af0c5305eba425b436077c
Timestamp: 1721228069 Timestamp [UCT]: 2024-07-17 14:54:29 Age [y:d:h:m:s]: 01:112:08:29:50
Block: 1067753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338777 RingCT/type: yes/0
Extra: 01af9a5baaa9cfc8d8a5893eff23d7d4fa859b2b69c5af0c5305eba425b436077c02110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2e16979ef474f7687bdf081de3bc041b84f76c21bb9526b3544bb0e6c223177 0.600000000000 1538652 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": 1067763, "vin": [ { "gen": { "height": 1067753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2e16979ef474f7687bdf081de3bc041b84f76c21bb9526b3544bb0e6c223177" } } ], "extra": [ 1, 175, 154, 91, 170, 169, 207, 200, 216, 165, 137, 62, 255, 35, 215, 212, 250, 133, 155, 43, 105, 197, 175, 12, 83, 5, 235, 164, 37, 180, 54, 7, 124, 2, 17, 0, 0, 0, 20, 145, 225, 60, 4, 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