Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8992ad5def2b03d2e3ad36ada37556b7ec002499637ddc40355c55332e9ac49

Tx prefix hash: 9d31a93f580e508a7201fb736af4cd42469726867d10c50d7ad2b16e7e7ad000
Tx public key: acd3defebcc415240aa9a3f862d3bcca256afb68dd37eb4d957b8d80906d8ec6
Timestamp: 1712046502 Timestamp [UCT]: 2024-04-02 08:28:22 Age [y:d:h:m:s]: 01:044:23:28:44
Block: 991593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293155 RingCT/type: yes/0
Extra: 01acd3defebcc415240aa9a3f862d3bcca256afb68dd37eb4d957b8d80906d8ec60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d887abeaef2de37d12b171f6b73ca8dcb56eb26e63afe179460bbd7c2679279 0.600000000000 1451929 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": 991603, "vin": [ { "gen": { "height": 991593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d887abeaef2de37d12b171f6b73ca8dcb56eb26e63afe179460bbd7c2679279" } } ], "extra": [ 1, 172, 211, 222, 254, 188, 196, 21, 36, 10, 169, 163, 248, 98, 211, 188, 202, 37, 106, 251, 104, 221, 55, 235, 77, 149, 123, 141, 128, 144, 109, 142, 198, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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