Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36d65c529af55a3e9697297728c659808f62afedc932326e79cca7414a79074

Tx prefix hash: 7e8c7c519d4610a7576e1a60b899dcce0afee7d4a509dbcede9fb68bd35debc8
Tx public key: e85ccec598f0d13e65f254ce34b32c14c44ca1b3921b8c70d9ceefd923d0da33
Timestamp: 1708981681 Timestamp [UCT]: 2024-02-26 21:08:01 Age [y:d:h:m:s]: 01:082:21:10:57
Block: 966218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320270 RingCT/type: yes/0
Extra: 01e85ccec598f0d13e65f254ce34b32c14c44ca1b3921b8c70d9ceefd923d0da330211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b83bc7a54a697076a80c1bf4857f97cd2f694f03cc93643ea7b04b725e6c9f33 0.600000000000 1425975 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": 966228, "vin": [ { "gen": { "height": 966218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b83bc7a54a697076a80c1bf4857f97cd2f694f03cc93643ea7b04b725e6c9f33" } } ], "extra": [ 1, 232, 92, 206, 197, 152, 240, 209, 62, 101, 242, 84, 206, 52, 179, 44, 20, 196, 76, 161, 179, 146, 27, 140, 112, 217, 206, 239, 217, 35, 208, 218, 51, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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