Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff742b25c5c1a92dbd63267557be539f0f548c41bf1757107e5f823f1494643a

Tx prefix hash: 9c674a8d5c45e498575d8149d4e91a5d42f0246394190f3434d9a4571738480f
Tx public key: f361746d0634aec3959a45d7fd7c771de6d2ee35717e6ca92ad7f45fb2cc2660
Timestamp: 1708636954 Timestamp [UCT]: 2024-02-22 21:22:34 Age [y:d:h:m:s]: 01:092:18:00:19
Block: 963348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327355 RingCT/type: yes/0
Extra: 01f361746d0634aec3959a45d7fd7c771de6d2ee35717e6ca92ad7f45fb2cc266002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b064ad75853ed14b9b4b60ed17b40b0d310aea5314f8811c4d4e9e1be47b40a7 0.600000000000 1423049 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": 963358, "vin": [ { "gen": { "height": 963348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b064ad75853ed14b9b4b60ed17b40b0d310aea5314f8811c4d4e9e1be47b40a7" } } ], "extra": [ 1, 243, 97, 116, 109, 6, 52, 174, 195, 149, 154, 69, 215, 253, 124, 119, 29, 230, 210, 238, 53, 113, 126, 108, 169, 42, 215, 244, 95, 178, 204, 38, 96, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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