Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d69e9fe8a12f5462d33d683dd3c3b7334c907530406a9deb7af170bccdc2e1

Tx prefix hash: 26ccc14210c89d410c18be9e3c6f0212fc794f17e99fd70ffa4672d8ed51d237
Tx public key: 2cdde9a83027bc0e91bae602cef64bb623913ddddf6bcbb70b01e8b1becfc7e1
Timestamp: 1700732128 Timestamp [UCT]: 2023-11-23 09:35:28 Age [y:d:h:m:s]: 01:348:08:15:13
Block: 897819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507834 RingCT/type: yes/0
Extra: 012cdde9a83027bc0e91bae602cef64bb623913ddddf6bcbb70b01e8b1becfc7e1021100000005faf35c9c000000000000000000

1 output(s) for total of 0.650358674000 dcy

stealth address amount amount idx
00: c886308d15efd3ed5816aecf62f224a88e7eced689832a6a1ae1e430571cea96 0.650358674000 1354214 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": 897829, "vin": [ { "gen": { "height": 897819 } } ], "vout": [ { "amount": 650358674, "target": { "key": "c886308d15efd3ed5816aecf62f224a88e7eced689832a6a1ae1e430571cea96" } } ], "extra": [ 1, 44, 221, 233, 168, 48, 39, 188, 14, 145, 186, 230, 2, 206, 246, 75, 182, 35, 145, 61, 221, 223, 107, 203, 183, 11, 1, 232, 177, 190, 207, 199, 225, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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