Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792faca9c6e0062d54c9c91dadab1f5ff209325d222ae4cbf2c8265228066e2f

Tx prefix hash: 4f3f37030e46d008bb76ef7f470d09474d59be29cd95d63356a52ea16c2da847
Tx public key: a2113d7b3ca66aa8ea77afb4ba6e87d5bf4ee80c731858662509a4b82c8200de
Timestamp: 1730148123 Timestamp [UCT]: 2024-10-28 20:42:03 Age [y:d:h:m:s]: 00:139:05:14:36
Block: 1141616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99332 RingCT/type: yes/0
Extra: 01a2113d7b3ca66aa8ea77afb4ba6e87d5bf4ee80c731858662509a4b82c8200de0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5526d97357e63af9bdf6b4a31b2bf995d4411f1d1af40ee42b29c2139b716157 0.600000000000 1625425 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": 1141626, "vin": [ { "gen": { "height": 1141616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5526d97357e63af9bdf6b4a31b2bf995d4411f1d1af40ee42b29c2139b716157" } } ], "extra": [ 1, 162, 17, 61, 123, 60, 166, 106, 168, 234, 119, 175, 180, 186, 110, 135, 213, 191, 78, 232, 12, 115, 24, 88, 102, 37, 9, 164, 184, 44, 130, 0, 222, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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