Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e99367af4e31b12f721943af0a9131b79d0e3d4d90cabb94b54b16a96a24a208

Tx prefix hash: fcf274f76e51c08514fbae846aa96283da8f8d618e0e69bfc3451f8e7acaa60c
Tx public key: 88a72fd90420d4e8dd5497d0d2af3d7505245c220c2a39c371e436c1e1b60026
Timestamp: 1708272392 Timestamp [UCT]: 2024-02-18 16:06:32 Age [y:d:h:m:s]: 01:348:00:41:21
Block: 960327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507413 RingCT/type: yes/0
Extra: 0188a72fd90420d4e8dd5497d0d2af3d7505245c220c2a39c371e436c1e1b6002602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07572deb55ab37742fd9ba171c04a8c5ecdf8f30493159535f6bb963daf07355 0.600000000000 1419890 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": 960337, "vin": [ { "gen": { "height": 960327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07572deb55ab37742fd9ba171c04a8c5ecdf8f30493159535f6bb963daf07355" } } ], "extra": [ 1, 136, 167, 47, 217, 4, 32, 212, 232, 221, 84, 151, 208, 210, 175, 61, 117, 5, 36, 92, 34, 12, 42, 57, 195, 113, 228, 54, 193, 225, 182, 0, 38, 2, 17, 0, 0, 0, 2, 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