Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f4eb008eec74c3491cc234bf4cf50ddd134045e180990a29a12c869617cbae6

Tx prefix hash: 41aa358d42078170d60ceda7318b5183a770621a3cd100a534375c10f888ed6a
Tx public key: cb86b02c7004ddb314ab2657286cd9e912fe341a80d0e963fda9b29c8a5d5d25
Timestamp: 1708587844 Timestamp [UCT]: 2024-02-22 07:44:04 Age [y:d:h:m:s]: 01:071:15:17:18
Block: 962939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312236 RingCT/type: yes/0
Extra: 01cb86b02c7004ddb314ab2657286cd9e912fe341a80d0e963fda9b29c8a5d5d250211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a299e8588d95b7a79e57b7fbce0f751be1f56f320bdd8f0998348b187dc86e8f 0.600000000000 1422628 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": 962949, "vin": [ { "gen": { "height": 962939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a299e8588d95b7a79e57b7fbce0f751be1f56f320bdd8f0998348b187dc86e8f" } } ], "extra": [ 1, 203, 134, 176, 44, 112, 4, 221, 179, 20, 171, 38, 87, 40, 108, 217, 233, 18, 254, 52, 26, 128, 208, 233, 99, 253, 169, 178, 156, 138, 93, 93, 37, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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