Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b36ecd1f8de3adf146b73f3fa87253c27bcebd0b2ce9201ad1efa3d480fdf10

Tx prefix hash: deb3615d70c5fdcf1d510db43a051622f3aa45bed5a316448264e8092e3344f8
Tx public key: 54bf64162e9579bee3fe3c7ab6e5f2d30a223ddc52d0263d941515923d926e66
Timestamp: 1733910409 Timestamp [UCT]: 2024-12-11 09:46:49 Age [y:d:h:m:s]: 00:189:00:03:00
Block: 1172780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134797 RingCT/type: yes/0
Extra: 0154bf64162e9579bee3fe3c7ab6e5f2d30a223ddc52d0263d941515923d926e66021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 187e25357bb05dbe9d6886d9c96d47959d5981aa3cbe7983efa615d690b435b7 0.600000000000 1658715 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": 1172790, "vin": [ { "gen": { "height": 1172780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "187e25357bb05dbe9d6886d9c96d47959d5981aa3cbe7983efa615d690b435b7" } } ], "extra": [ 1, 84, 191, 100, 22, 46, 149, 121, 190, 227, 254, 60, 122, 182, 229, 242, 211, 10, 34, 61, 220, 82, 208, 38, 61, 148, 21, 21, 146, 61, 146, 110, 102, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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