Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5138acbca417f749bdf044d77fc7d298d6b4859cad16959071dc893b17f71c58

Tx prefix hash: 0f56ece042234698e57cfbc27909e12b40dce62accf9ac1cb54224e51512c755
Tx public key: ce9c7984a45f36e98c2c71049d197a90013f3f0fc0114f982c7bab0a2b042919
Timestamp: 1701677169 Timestamp [UCT]: 2023-12-04 08:06:09 Age [y:d:h:m:s]: 01:341:08:27:48
Block: 905639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502853 RingCT/type: yes/0
Extra: 01ce9c7984a45f36e98c2c71049d197a90013f3f0fc0114f982c7bab0a2b04291902110000000233af99f4000000000000000000

1 output(s) for total of 0.612691732000 dcy

stealth address amount amount idx
00: 74f69f110c2c0c25cf77c3d7b7acc2219d875ee27b46b4961e86149d51362a7c 0.612691732000 1362534 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": 905649, "vin": [ { "gen": { "height": 905639 } } ], "vout": [ { "amount": 612691732, "target": { "key": "74f69f110c2c0c25cf77c3d7b7acc2219d875ee27b46b4961e86149d51362a7c" } } ], "extra": [ 1, 206, 156, 121, 132, 164, 95, 54, 233, 140, 44, 113, 4, 157, 25, 122, 144, 1, 63, 63, 15, 192, 17, 79, 152, 44, 123, 171, 10, 43, 4, 41, 25, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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