Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5c548aa11f4d85a95b3c5d9799c847104f472982b93e79dfea5768231d7b2c

Tx prefix hash: 71879d801a4cabafb8e5b821dcdafed87a60cd896b7e53dafecd35db80736fa8
Tx public key: 47a5cd43571abfd0c43a23f3b7415cde9a78e6396a0fe5bc345572dfd3c942e1
Timestamp: 1722592171 Timestamp [UCT]: 2024-08-02 09:49:31 Age [y:d:h:m:s]: 01:096:09:31:37
Block: 1079043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327368 RingCT/type: yes/0
Extra: 0147a5cd43571abfd0c43a23f3b7415cde9a78e6396a0fe5bc345572dfd3c942e102110000000991e13c04000000000000000000

1 output(s) for total of 0.615620000000 dcy

stealth address amount amount idx
00: 0ed0eb2314437b90914e1b2fba5a7278f1ae9c3bfd224c7f904e933a700c41f1 0.615620000000 1551828 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": 1079053, "vin": [ { "gen": { "height": 1079043 } } ], "vout": [ { "amount": 615620000, "target": { "key": "0ed0eb2314437b90914e1b2fba5a7278f1ae9c3bfd224c7f904e933a700c41f1" } } ], "extra": [ 1, 71, 165, 205, 67, 87, 26, 191, 208, 196, 58, 35, 243, 183, 65, 92, 222, 154, 120, 230, 57, 106, 15, 229, 188, 52, 85, 114, 223, 211, 201, 66, 225, 2, 17, 0, 0, 0, 9, 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