Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d477652ce3f9e2b400955f3c23bdaa19cf059c9d2fe308def956b5109461abad

Tx prefix hash: 79a1ddb2f4d4fed13e6ab6b44cd797c1995d91951a13718579dae48be012463e
Tx public key: f0e86f4dcf0d6a83d77744ae9c5bd037e52013268c200e26860582f605676a5c
Timestamp: 1626848091 Timestamp [UCT]: 2021-07-21 06:14:51 Age [y:d:h:m:s]: 03:170:02:53:29
Block: 298045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893316 RingCT/type: yes/0
Extra: 01f0e86f4dcf0d6a83d77744ae9c5bd037e52013268c200e26860582f605676a5c0211000000146367b7e9000000000000000000

1 output(s) for total of 63.161681594000 dcy

stealth address amount amount idx
00: 197da748d814c5c9b6b0d6775253ee7683e06d78ebf89f565dcae159f3de472f 63.161681594000 623724 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": 298055, "vin": [ { "gen": { "height": 298045 } } ], "vout": [ { "amount": 63161681594, "target": { "key": "197da748d814c5c9b6b0d6775253ee7683e06d78ebf89f565dcae159f3de472f" } } ], "extra": [ 1, 240, 232, 111, 77, 207, 13, 106, 131, 215, 119, 68, 174, 156, 91, 208, 55, 229, 32, 19, 38, 140, 32, 14, 38, 134, 5, 130, 246, 5, 103, 106, 92, 2, 17, 0, 0, 0, 20, 99, 103, 183, 233, 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