Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac67bb5e0970e3eedbfb7bc6109d79e5262b047192707c3a3d8d8633c249c39e

Tx prefix hash: 41be903eaa7c28ffd8025429ed44937b068511b99c760de0bb2ae42981425b04
Tx public key: 8ae8128ec9ab1764281408a739e57726178c3da02ef9341873cb9a2f5e817b03
Timestamp: 1696028984 Timestamp [UCT]: 2023-09-29 23:09:44 Age [y:d:h:m:s]: 02:037:15:19:36
Block: 859028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546522 RingCT/type: yes/0
Extra: 018ae8128ec9ab1764281408a739e57726178c3da02ef9341873cb9a2f5e817b030211000000024b8f5122000000000000000000

1 output(s) for total of 0.874346709000 dcy

stealth address amount amount idx
00: 5920a7cf519445f99bf9c0b1ec4f59da4c982f820bfb7c6bfd27636f999907ea 0.874346709000 1313234 of 0

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": 859038, "vin": [ { "gen": { "height": 859028 } } ], "vout": [ { "amount": 874346709, "target": { "key": "5920a7cf519445f99bf9c0b1ec4f59da4c982f820bfb7c6bfd27636f999907ea" } } ], "extra": [ 1, 138, 232, 18, 142, 201, 171, 23, 100, 40, 20, 8, 167, 57, 229, 119, 38, 23, 140, 61, 160, 46, 249, 52, 24, 115, 203, 154, 47, 94, 129, 123, 3, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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