Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b39c9e01a1d6c26b0201b1f136ed0df372d56f0905aa88e0f94f77f431d2d434

Tx prefix hash: f5a2cd94f0909691d24c296f00641641105a72daa1ae43bb10e91f960ee1cc1c
Tx public key: d30e6704b175eafcf24d49c08a406bc8a01059e8d8f945952055a67ddd809cc1
Timestamp: 1708962891 Timestamp [UCT]: 2024-02-26 15:54:51 Age [y:d:h:m:s]: 01:258:17:17:21
Block: 966059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443638 RingCT/type: yes/0
Extra: 01d30e6704b175eafcf24d49c08a406bc8a01059e8d8f945952055a67ddd809cc102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca0e4fe7be4a3a054a2a049534611df963a91d8115c9666e3c9bead06576b340 0.600000000000 1425816 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": 966069, "vin": [ { "gen": { "height": 966059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca0e4fe7be4a3a054a2a049534611df963a91d8115c9666e3c9bead06576b340" } } ], "extra": [ 1, 211, 14, 103, 4, 177, 117, 234, 252, 242, 77, 73, 192, 138, 64, 107, 200, 160, 16, 89, 232, 216, 249, 69, 149, 32, 85, 166, 125, 221, 128, 156, 193, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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